Description

This PR is still in progress. The changes are not final and are for testing purposes only

Address memory exhaustion issues when uploading large numbers of files (e.g., 2000+ small files) on low-RAM machines by implementing adaptive concurrency controls and fixing stream reader leaks.

Changes:

• Fix stream reader memory leak in crypto.ts by properly releasing readers using try-finally block to ensure cleanup even on errors
• Add adaptive concurrency to UploadManager based on system RAM (2-6 concurrent uploads depending on available heap size)
• Add adaptive concurrency to UploadFoldersManager for folder operations (2-6 concurrent folder uploads based on system capabilities)
• Implement smart file batching when memory usage exceeds 80% (splits large file sets into batches of 100 with 200ms delays)

Impact:

• High-RAM machines (≥4 GB heap): Maintain full performance with 6 concurrent uploads
• Medium-RAM machines (2-4 GB heap): Use 4 concurrent uploads
• Low-RAM machines (<2 GB heap): Use 2 concurrent uploads to prevent freezing
• Memory leak fix prevents ~500 KB retention per file upload

Resolves memory exhaustion and browser freezing on low-spec machines while
maintaining optimal performance on high-end systems.

Related Issues

Related Pull Requests

Checklist

• Changes have been tested locally.
• Unit tests have been written or updated as necessary.
• The code adheres to the repository's coding standards.
• Relevant documentation has been added or updated.
• No new warnings or errors have been introduced.
• SonarCloud issues have been reviewed and addressed.
• QA Passed

Testing Process

Additional Notes